From: Joey Hess Date: Tue, 7 Jan 2025 20:50:37 +0000 (-0400) Subject: comment X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~10^2~31 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:///%22http:/www.example.com/cgi/%22https:/www.github.com/%22bookmarks:/?a=commitdiff_plain;h=5d478ec38e74016812753f4b5ca951b79b322daf;p=git-annex.git comment --- diff --git a/doc/bugs/keeps_ext_remote_after_all_urls_unregistered/comment_3_9d724cfc7248319dcad3b57db24118fd._comment b/doc/bugs/keeps_ext_remote_after_all_urls_unregistered/comment_3_9d724cfc7248319dcad3b57db24118fd._comment new file mode 100644 index 0000000000..1423c8377f --- /dev/null +++ b/doc/bugs/keeps_ext_remote_after_all_urls_unregistered/comment_3_9d724cfc7248319dcad3b57db24118fd._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2025-01-07T20:40:02Z" + content=""" +It would need some way for a special remote to indicate to git-annex that +it is in this unusual class of remotes where not having an url is the same as +content no longer being present in it. + +Implementing that would just make some more remotes have a special case, +which seems even harder to remember. I'd rather remove the special case, +but of course that will break existing workflows. + +And it is unusual. Consider a S3 remote. It can have an url recorded for a +object stored in it, but forgetting the url doesn't mean that the S3 bucket +no longer contains the file. If git-annex behaved this way for S3, it would +be broken in a way that could be expensive to the user. + +(The special case is not currently implemented for bittorrent special +remote. But it also doesn't record urls in a user-visible way actually.) +"""]]